Developer CD Series 1997 January: Mac OS SDK/Dev.CD Jan 97 SDK2.toast/Development Kits (Disc 2)/OpenDoc Development Framework/ODF-Interest Archive/August 96/OpenDoc & SOM Memory Allocation

Internet Message Format | 1996-08-19 | 1.5 KB | [TEXT/ttxt]

Subject:     OpenDoc & SOM Memory Allocation
Sent:        8/14/96 12:11 PM
Received:    8/14/96 12:31 PM
From:        John Casey, [e-mail]
Reply-To:    ODF Interest, [e-mail]
To:          OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.


When passing data back and forth between OpenDoc parts and Extensions,
there is a clear definition of who needs to allocate and free memory.
Memory is always allocated by the sending object and deleted by the
receiving object.  ODF's FW_CByteArray can be used to help automate this
process.

When attempting to use the same convention for communicating with
SOMObjects, I have run into problems with ODF's delete operator override.
 Since my SOM Object does not use OpenDoc's Memory Manager, the new
performed by the SOMObject is not handled properly when attempting to
delete the received data in the OpenDoc Part.  To complicate problems, it
appears that CodeWarrior's C++ compiler ignores the scope operator when I
attempt to bypass OpenDoc's Memory manager by calling ::delete.

So ..... what is the "official" convention for memory management of data
passed between OpenDoc Parts and SOMObjects?


===========================================================================
=
John Casey                                     Mail: [e-mail]
Vice President                                 Web:
http://www.ncs-ssc.com
Nation Computer Services                       FAX:  [phone]
===========================================================================
=